Fix fixed cost description for Application Gateway V2 #127592
Conversation
As we confirmed , no matter AppGW stoped or started, the public IP still be charged by time. so this contents need to be modify.
prmerger-automator
bot
requested review from
AbdullahBell,
cherylmc and
mbender-ms
|
@Tanharuki : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 90ee94e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
Can you review this old PR and determine whether it needs to be closed or merged? @MicrosoftDocs/public-repo-pr-review-team |
There was a problem hiding this comment.
Pull Request Overview
This PR corrects the description of fixed costs for Application Gateway V2 to accurately reflect that public IP address charges are billed separately and not included in the gateway's fixed costs.
Key Change:
- Updated the fixed cost documentation to clarify that public IP address costs are separate from Application Gateway V2 fixed costs
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
|
||
| - **Fixed costs**: These costs are based on the time the Application Gateway V2 or WAF V2 is provisioned and available for processing requests. This ensures high availability. There's an associated cost even if zero instances are reserved by specifying `0` in the minimum instance count, as part of autoscaling. | ||
| - The fixed cost also includes the cost associated with the public IP address attached to the application gateway. | ||
| - The fixed cost does not includes the cost associated with the public IP address attached to the application gateway. |
There was a problem hiding this comment.
Grammatical error: 'does not includes' should be 'does not include' (singular form after 'does not').
| - The fixed cost does not includes the cost associated with the public IP address attached to the application gateway. | |
| - The fixed cost does not include the cost associated with the public IP address attached to the application gateway. |
|
|
||
| - **Fixed costs**: These costs are based on the time the Application Gateway V2 or WAF V2 is provisioned and available for processing requests. This ensures high availability. There's an associated cost even if zero instances are reserved by specifying `0` in the minimum instance count, as part of autoscaling. | ||
| - The fixed cost also includes the cost associated with the public IP address attached to the application gateway. | ||
| - The fixed cost does not includes the cost associated with the public IP address attached to the application gateway. |
There was a problem hiding this comment.
| - The fixed cost does not includes the cost associated with the public IP address attached to the application gateway. | |
| - The fixed cost does not include the cost associated with the public IP address attached to the application gateway. |
Please commit update and then this can be signed off @Tanharuki. Thanks!
There was a problem hiding this comment.
@Tanharuki - Can you respond to the requested changes or let us know if you would like us to commit them?
@mbender-ms - When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team
3 participants
As we confirmed , no matter AppGW stoped or started, the public IP still be charged by time. so this contents need to be modify.
"The fixed cost also includes the cost associated with the public IP address attached to the application gateway."
should be "The fixed cost dose not includes the cost associated with the public IP address attached to the application gateway."